Documentation PR Review

Editorial Review

docs/passwordsecure/current/configuration/webapplication/web_application.md

• Clarity — Line 28: The new UI lock section calls the product "web app" ("the Netwrix Password Secure web app"), but the rest of this document consistently uses "Web Application" / "Netwrix Password Secure Web Application". Introducing a third variant ("web app") makes it momentarily unclear that this is the same component. Suggested fix: "When you refresh the Netwrix Password Secure Web Application or click the Lock entry in the menu..."
• Structure — Line 27: "UI lock" is added as an ### H3 nested under the "What is the Web Application" overview. That section describes what the Web Application is at a high level; a specific behavioral feature reads as out of place buried there. A reader scanning for feature behavior won't expect to find it inside the introduction. Suggested fix: promote "UI lock" to its own ## H2 section placed after the overview. Also add a blank line between the ### UI lock heading and the paragraph that follows it.
• Completeness — Line 30: "your second factor isn't required" references a second authentication factor without context. Per the audience guidance, newer users may not connect this to MFA. Suggested fix: "your second authentication factor (MFA) isn't required."

docs/passwordsecure/current/introduction/versionhistory/version_26.6.100.34161.md

• Clarity — Line 9: "This release brings in some breaking changes" — "brings in" is informal for a changelog warning. Suggested fix: "This release introduces breaking changes..."
• Clarity — Lines 29, 57–58: The changelog refers to the same component inconsistently as "web app" (line 29) and "web application" (lines 57–58), while the section headings use "Web application". Suggested fix: standardize on "Web Application" throughout the body.

docs/passwordsecure/current/introduction/versionhistory/version_history.md

• No issues found.

Summary

5 editorial suggestions across 2 files. Vale and Dale issues are auto-fixed separately.

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

Auto-Fix Summary

5 issues fixed, 2 skipped across 3 files

| docs/passwordsecure/current/configuration/webapplication/web_application.md:11 — Dale: wordiness | 'serves as the basis for the constant enhancement of the functional scope' and the surrounding repetition is wordy, but rewriting risks changing the author's intended meaning about ongoing enhancement |
| docs/passwordsecure/current/configuration/webapplication/web_application.md:30 — Dale: passive-voice | 'your second factor isn't required' is a stative passive that reads naturally; rewriting is optional and could subtly shift emphasis |

Ask @claude on this PR if you'd like an explanation of any fix.

Code Review

I reviewed the non-documentation changes (issue templates, config/routing impact, and build-affecting items). Per scope, I did not review prose content or style.

No correctness, build, or workflow issues found.

Details of what I checked:

• Issue templates (contend_add.yml, content_fix.yml): Removing Password Secure 9.1 / Password Secure 26.3 and adding Password Secure Current correctly aligns the dropdown with src/config/products.js, which defines Password Secure versions as current, 9.3, and 9.2 only. Both dropdowns use multiple: true with no default: index, so removing options does not shift any index-based default. Safe.
• New version file + index link: version_history.md links to the new version_26.6.100.34161.md, which exists, so the onBrokenLinks: 'throw' build will not fail. sidebar_position: 7 is unique and follows the existing descending-by-recency ordering (8, 9, 10, 20).
• Internal links in web_application.md (functional_scope.md, installation_web_application.md) resolve to existing files.
• MDX safety: The only angle-bracket usage in the new content is self-closing <br /> tags, which are valid MDX. No bare < that could be misparsed as JSX.

No changes to docusaurus.config.js, sidebars, the KB copy pipeline, or CI/CD workflow logic in this PR.